home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Supervisor's Toolkit
/
Network Supervisor's Toolkit.iso
/
novell
/
fyicom
/
fyi_su.net
< prev
next >
Wrap
Text File
|
1996-07-10
|
13KB
|
436 lines
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS V2 and Mirror from SoftKlone
DOCUMENT ID#: FYI.S.NACS01
DATE: 06AUG91
PRODUCT: NACS
PRODUCT VERSION: v2.09
SUPERSEDES: NA
SYMPTOM
Script stops
ISSUE/PROBLEM
The program Mirror (SoftKlone Industries (904) 878-8564), a
Minitel emulator, had a problem interpreting a string from
NASI. It appears that the program receives a "@" character
from NASI or the interface SoftKlone built to hook NASI. A
script was waiting for a particular character string and the
"@" symbol stopped the script.
SOLUTION
A wait string for the "@" character and then a GOTO statement
for the original wait string.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS and Crosstalk Mark IV - "NACS is not
responding"
DOCUMENT ID#: FYI.S.NACS02
DATE: 15NOV91
PRODUCT: NACS02
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM
Error stating that the NACS is not responding
ISSUE/PROBLEM
Crosstalk has a setting for NASI. If this is chosen, a field
appears prompting for a server name. It appears to require
the NACS server name, but it does not. It needs the Specific
or General name of a NACS port. If the NACS server name is
entered, an error appears stating that the NACS is not
responding.
SOLUTION
Try a NACS port name in the server name field before
troubleshooting the NACS. What Crosstalk requires is a
SERVICE name on the NACS.
It is expected that the publisher of Crosstalk will change
this in a future release.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS and Crosstalk Mark IV, File Share
Violation Errors
DOCUMENT ID#: FYI.S.NACS03
DATE: 15NOV91
PRODUCT: NACS
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM
File share violation errors
ISSUE/PROBLEM
File share violation errors when multiple numbers of users use
Crosstalk.
SOLUTION
Solution 1. Copy all Crosstalk files except the EXE to
unique directory for each user.
Solution 2. Have users run Crosstalk from the local drive.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS, NASI, and Y modem protocol
DOCUMENT ID#: FYI.S.NACS04
DATE: 15NOV91
PRODUCT: NACS
PRODUCT VERSION: v2x
SUPERSEDES: NA
SYMPTOM
Unable to upload with the YModem Protocol
ISSUE/PROBLEM
NASI's maximum write data buffer size is 498 bytes and maximum
read data buffer size is 512 bytes. Ymodem and Ymodem G
protocol use 512 bytes. Therefore, Y modem can be used to
download but not upload.
SOLUTION
Download NACS2.ZIP in order to upgrade to a later version of
NACS/NASI2.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS and OS/2
DOCUMENT ID#: FYI.S.NACS05
DATE: 11JUN92
PRODUCT: NACS
PRODUCT VERSION: Before v2.09
SUPERSEDES: NA
SYMPTOM
NASI would not dial out from OS/2
ISSUE/PROBLEM
Failure dial out through NACS V2.x loading NASI and ProCom+ in
the OS/2 workstation DOS Box.
SOLUTION
1. Upgrade to OS/2 2.0, using the latest requester for 2.0.
2. Upgraded to NACS/NASI version 2.09
3. Inside OS/2 set "Global Network Support."
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS, Anywhere 4 LAN+net addresses
DOCUMENT ID#: FYI.S.NACS06
DATE: 06JUL92
PRODUCT: NACS
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM
"Modem not responding"
ISSUE/PROBLEM
Anywhere for LAN is just as subject to network address
conflicts as a router. You can attach to a port; however, if
there is an address conflict, the following message will be
displayed:
┌────────────────────┐
│Modem not responding│
└────────────────────┘
SOLUTION
Make certain there are no duplicate network addresses.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: LC:Unable to Build Streams for Service SPX,
error code 910h
DOCUMENT ID#: FYI.S.NACS07
DATE: 10JUL92
PRODUCT: NACS
PRODUCT VERSION: v3
SUPERSEDES: NA
SYMPTOM
LC:unable to build streams for service SPX, error code 910h
ISSUE/PROBLEM
Page 4-7 of the NACS Administration Guide tells the
installer to "load SPX." However, if COMMEXEC is loaded it
returns the following error:
┌──────────────────────────────────────────────────────
─────┐
│LC:unable to build streams for service SPX, error code
910h│
└──────────────────────────────────────────────────────
─────┘
The CS prompt does come up and NACS can be loaded. The NACS
appears to work but COMEX.CSC (NACS autoloader) does not run.
SOLUTION
The guide is not correct. It should say "load SPXS."
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS with DigiBoard PC/Xe Boards
DOCUMENT ID#: FYI.S.NACS08
DATE: 14MAY92
PRODUCT: NACS
PRODUCT VERSION: v3x
SUPERSEDES: NA
SYMPTOM
LC: Unload from NetWare console of service:NACS
ISSUE/PROBLEM
The DigiBoards would initialize and everything seemed fine
until CSSTATUS was loaded and CSLOAD NACS was typed. Then the
following error message was received:
┌───────────────────────────────────────────────┐
│LC: Unload from NetWare console of service:NACS│
└───────────────────────────────────────────────┘
SOLUTION
Add the statement NODE=0 to the AUTOEXEC.NCF so that it reads
as follows:
load aiodgxi port=xxxx mem=xxxxx node=0
Note: This command must be in lowercase.
According to DigiBoard documentation, you need to add NODE=0
to AIO drivers 1.0.2 or earlier. The driver on DigiBoards BBS
dated 05-28-92 is version 1.0.1 and is certified.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: NACS with DigiBoard PC/Xe Boards
DOCUMENT ID#: FYI.S.NACS09
DATE: 18JUN92
PRODUCT: NACS
PRODUCT VERSION: v3x
SUPERSEDES: NA
SYMPTOM
Bad CRC counts and file transfer abort "LC: Unload from
Netware console of service:NACS"
ISSUE/PROBLEM
With NACS containing DigiBoard PC/XEs, an attempt to download
(only) a binary (only) file resulted in numerous bad CRC
counts and the file transfer would abort with the following
message:
┌───────────────────────────────────────────────┐
│LC: Unload from Netware console of service:NACS│
└───────────────────────────────────────────────┘
The problem occurred regardless of modem protocol.
SOLUTION
Contact DigiBoard Inc. to replace the driver. Drivers dated
05-28-92 or later should be fine. BBS Phone 612-943-0812
Voice 612-493-9020
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: Printing with 3270 LAN Workstation for Windows
DOCUMENT ID#: FYI.S.SAA39
DATE: 22DEC92
PRODUCT: 3270 LAN Workstation for Windows
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM
Escape sequence problems
ISSUE/PROBLEM
The 3270 LAN Workstation for Windows utilizes Microsoft's
Windows printer drivers for host (LU1 and 3) printing.
The interrelationship between the Workstation and the Windows
printer drivers results in problems with the insertion of
escape sequences through LU1 transparently into the printer
datastream.
SOLUTION
A workaround is to use a PASSTHROUGH call to the Windows
printer drivers.
However, because of the way the Windows printer drivers buffer
the entire page of text, this results in all escape sequences
and transparent data being sent at the start of each page
before the text and initialization control codes (which will
then override the escape sequences).
Contact with Microsoft indicates that the problem will not be
corrected by any contemplated change in the Windows printer
drivers.
Changing 3270 LAN Workstation for Windows to support IPDS
(Intelligent Printer Data Stream) would correct the problem.
Such a change is being considered.
Users have two options for a complete solution:
1. Purchase NetWare HostPrint, and print using it thereby
bypassing the Windows printer drivers.
2. Purchase a third-party product that supports IPDS such as
Dr. Materna's Windows emulator.
FYI
(Note: The origin of this information may be internal or external
to Novell. Novell makes every effort within its means to verify
this information. However, the information provided in this
document is FOR YOUR INFORMATION only. Novell makes no explicit or
implied claims to the validity of this information.)
TITLE: WAN Routers with Everex AGI3000G
DOCUMENT ID#: FYI.S.WAN03
DATE: 07FEB91
PRODUCT: All WAN Routers
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM
Various
ISSUE/PROBLEM
During 1991 problems were reported running WAN routers with
more than WNIC in Everex 386 AGI3000G machines. Both the
small footprint SX and large footprint DX machines had
problems.
SOLUTION
NA